Skip to content

fix(build): Namespace snapshot object keys by org and project#3166

Closed
runningcode wants to merge 1 commit intomasterfrom
no/namespace-snapshot-object-keys
Closed

fix(build): Namespace snapshot object keys by org and project#3166
runningcode wants to merge 1 commit intomasterfrom
no/namespace-snapshot-object-keys

Conversation

@runningcode
Copy link
Copy Markdown
Contributor

What

Snapshot images are now stored using {org_id}/{project_id}/{hash} as the object key instead of just {hash}.

Why

Using only the SHA256 hash as the object key could cause collisions or unintended sharing of objects across organizations and projects that happen to upload identical files.

Previously, snapshot images were stored using only their SHA256 hash as
the object key. This could cause collisions or incorrect sharing of
objects across organizations and projects with identical file contents.

Now keys are scoped as `{org_id}/{project_id}/{hash}` to ensure proper
isolation in the object store.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 2, 2026

Fails
🚫 Please consider adding a changelog entry for the next release.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

### Fixes

- Namespace snapshot object keys by org and project ([#3166](https://github.com/getsentry/sentry-cli/pull/3166))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description or adding a skip-changelog label.

Generated by 🚫 dangerJS against e06ae42

@runningcode runningcode closed this Mar 2, 2026
@runningcode runningcode deleted the no/namespace-snapshot-object-keys branch March 2, 2026 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant